From 3bd39c408e936a3040dd89491cb3ea5f5ad06429 Mon Sep 17 00:00:00 2001 From: "kfraser@localhost.localdomain" Date: Tue, 13 Mar 2007 09:52:11 +0000 Subject: [PATCH] docs: update some todo items. Signed-off-by: Stefan Berger --- docs/xen-api/todo.tex | 11 ++--------- 1 file changed, 2 insertions(+), 9 deletions(-) diff --git a/docs/xen-api/todo.tex b/docs/xen-api/todo.tex index 6f679ca01e..b66dec0aba 100644 --- a/docs/xen-api/todo.tex +++ b/docs/xen-api/todo.tex @@ -91,17 +91,10 @@ same subnet. \end{itemize} -\item TPM +\item ACM \begin{itemize} -\item Would it not be better to have a class TPM and a member TPMs ((TPM ref) -Set) containing an array of zero or one references to TPMs? I assume that -an empty array would make it clear that no TPM is associated with the VM -instead of encoding its existence into TPM/instance or TPM/backend -somehow. The current members instance and backend could then be moved into -the TPM class. - -\item Also a Xen system can be running an access control policy where each +\item A Xen system can be running an access control policy where each VM's run-time access to resources is restricted by the label it has been given compared to those of the resources. Currently a VM's configuration file may contain a line like access\_control[policy='$<$name of the system's -- 2.30.2